The Ansible package module args are passed as JSON.stringify(moduleArgs) to the -a flag. However, Ansible's ad-hoc command syntax typically expects module arguments in a different format (key=value pairs). The correct format should be either using --args with proper quoting, or converting the moduleArgs object to key=value format. For example, the command should look like: ansible host -m package -a "name=curl state=present" not ansible host -m package -a '{"name":"curl","state":"present"}'. This will likely cause Ansible to fail with a parsing error.

@copilot open a new pull request to apply changes based on this feedback

Same issue here - passing an empty string when currentExecutionId is falsy. The component should either handle empty executionId properly or this component should only be rendered when there's a valid executionId available.

@copilot open a new pull request to apply changes based on this feedback

The migration adds the execution_tool column without a CHECK constraint, while the schema.sql file (line 19) includes CHECK(execution_tool IN ('bolt', 'ansible')). This mismatch means that existing databases upgraded via migration won't have the constraint enforced, while fresh installations will. Consider adding the CHECK constraint in the migration as well: ALTER TABLE executions ADD COLUMN execution_tool TEXT DEFAULT 'bolt' CHECK(execution_tool IN ('bolt', 'ansible'));

The classes field is added to the interface but it's optional. When no classes are found (e.g., no catalog available), this field is set to an empty array [] in the HieraService. However, the frontend NodeHieraTab component checks if (hieraData.classes && hieraData.classes.length > 0) which means an empty array will render the "No catalog classes found" warning. This is correct behavior, but consider documenting in the type definition that an empty array indicates "catalog was checked but no classes found" versus undefined meaning "classes not available".

The executeAction method only takes the first target when action.target is an array (action.target[0]). While this is documented in error messages, Ansible actually supports running commands against multiple hosts. The current implementation silently ignores additional targets in the array. Consider either: 1) explicitly documenting this limitation and throwing an error when multiple targets are provided, or 2) implementing proper multi-target support by using Ansible patterns or looping through targets.

The validation logic if (selectedTool === 'bolt' && !selectedTask) on line 114 should also check if selectedTask is an empty string, not just falsy. An empty string would pass this check but fail to find a valid task. Consider using if (selectedTool === 'bolt' && (!selectedTask || !selectedTask.trim())).

The Node interface in bolt/types.ts supports "docker" transport (line 109), but the AnsibleService.getInventory() method only maps "ssh", "winrm", and "local" transports (lines 362-368). If Ansible is configured to use Docker as a connection type (ansible_connection=docker), it will default to "ssh" which is incorrect. Consider adding support for "docker" transport or explicitly handling unmapped connection types with a warning.

The title changed from "Pabawi zero" to "Pabawi Zero" (capitalizing the Z). While this is a stylistic choice, ensure this is intentional and consistent with branding. The acronym expansion below was also updated from "Puppet And Bolt Awesome Web Interface" to "Puppet Ansible Bolt Awesome Web Interface". Note that this changes the meaning of the 'A' in PABAWI from "And" to "Ansible", which may confuse existing users. Consider whether this rebrand needs documentation or announcement.

These new info logs (Date range: ..., Converted to ... days) will run on every aggregated-history request and can add significant noise in production. Consider downgrading them to debug (or gating behind expert mode) so normal info logs stay high-signal.

@copilot open a new pull request to apply changes based on this feedback

getNodeFacts() spawns an ansible process without any timeout/kill logic. If the SSH connection hangs or Ansible stalls, this promise can block indefinitely and leak a child process. Add a timeout similar to checkBinary()/AnsibleService.executeCommand() (kill the child on expiry) and reject with a clear error.

No automated tests were added for the new playbook execution endpoint. Since this introduces a new public API surface and async execution flow (execution record creation + streaming completion/error updates), add backend tests covering: 202 response with executionId, 503 when Ansible tool unavailable, 404 for unknown node, and successful completion updating the execution record.

UI tagline text is missing punctuation/grammar ("Puppet Ansible Bolt Awesome Web Interface"). Consider adding commas/"and" for readability (e.g., "Puppet, Ansible, and Bolt Awesome Web Interface").

getIncludedClasses() assumes resourcesByType.Class exists; when PuppetDB returns no Class key this becomes undefined, triggering an exception on .length/.map and forcing the catch-path. Default classResources to an empty array (e.g., resourcesByType.Class ?? []) so the no-classes case is handled without throwing and without misleading error logs.

Logging the full class list at info level (All classes: ...) can produce extremely large log lines on real catalogs, impacting log volume and readability. Consider logging only a count (and maybe a small sample) at info level, and put the full list behind debug logging (or omit entirely).

This new date-range log is emitted at info level on every aggregated history request. It’s likely too noisy for production logs; consider changing it to debug-level (or gating it behind expert mode) so normal operation doesn’t spam logs.

Same as above: Converted to X days of history is info-level and will be logged on every call. Consider lowering to debug-level or removing once the date-range fix is validated.

For Ansible ad-hoc usage, -a module arguments for the package module are not JSON; Ansible expects a key=value string (or YAML-style args), so JSON.stringify(moduleArgs) is very likely to fail at runtime. Convert moduleArgs to the expected key=value format (and ensure values are properly quoted/escaped).

The regex used to extract ansible_facts is non-brace-aware and will stop at the first } inside the facts object, which will make JSON.parse fail or produce truncated data for real-world nested facts. Instead, parse the full JSON object from Ansible output (e.g., extract the JSON payload after => and parse it, or force JSON stdout callback), then read ansible_facts from the parsed structure.

resourcesByType.Class may be undefined when PuppetDB returns no Class resources, which would throw when accessing .length and break Hiera data for that node. Default this to an empty array (e.g., resourcesByType.Class ?? []) before using it.